|
|
|
|
|
|
|
The initializeSystem method is responsible for safely starting up the system, including global variables. It is equivalent to the Form_Load or Class_Initialize events. The terminateSystem method is responsible for doing the reverse of the initializeSystem method. The terminateSystem method is equivalent to the Form_Unload and Class_Terminate events. The getAppState method is an accessor that returns the state of the application at any point to the client. The setAppState mutator method enables a client to set the state of the application. Ideally, the application's state should only be updated by subsystem interface classes as such classes will have a better understanding of the state of the application than any underlying class. The login and logoff methods are purely optional and are meant to delegate their respective duties to the Workgroup and User Security Subsystem. |
|
|
|
|
|
|
|
|
The class AppTransactions has the following methods: |
|
|
|
|
|
|
|
|
The activateLogging and deactivateLogging methods are responsible for activating and deactivating, respectively, the recording of transactions and memory allocations for variables. These methods are helpful when you want to manage whether targeted application events are being logged. For instance, if you notice performance degradation in certain environments, you can turn off the logging feature by accessing these methods. |
|
|
|
|
|
|
|
|
The addTrans2List,addTrans2MemLog, and addTrans2Text methods are three of the same kinds of methods that are responsible for logging transactions and memory allocations. I already discussed the addTrans2MemLog method. What was not revealed was that |
|
|
|
|
|